VIRTUS Protocol — Structure Overview
Version: 1.0
Table of Contents
1. Introduction
1.1 What Is VIRTUS Protocol
VIRTUS Protocol is a decentralized exchange and liquidity marketplace deployed on Base, an Ethereum Layer 2 Optimistic Rollup. It combines automated market maker (AMM) functionality with a vote-escrow governance model (ve(3,3)), enabling users to swap tokens, provide liquidity, and participate in protocol governance — all without intermediaries or centralized custody.
The protocol operates without venture capital backing and without token sales. It is maintained and governed by its community of token holders and liquidity providers.
A token of integrity — Powered by us.
1.2 Core Architecture
The protocol consists of five core layers:
Dashboard — A unified view of protocol metrics (TVL, volume, fees) and individual portfolio positions.
Swap — Two trading engines: an on-chain LP Swap for pairs hosted in VIRTUS liquidity pools, and a Multichain Swap aggregator (powered by Rango and LiFi) for cross-chain routing across supported networks.
Pool — Liquidity providers deposit assets into pools and earn either trading fees (if unstaked) or VRT emissions (if staked in a gauge). Pool types include stable (correlated assets), volatile (standard x·y=k for uncorrelated assets), and concentrated liquidity (Slipstream CL pools for capital-efficient price ranges). Blue Fish Pools (WETH/USDC, cbBTC/USDC, WETH/cbBTC) serve as the protocol's primary liquidity backbone.
Governance — VRT holders lock tokens to receive veVRT (an ERC-721 NFT), which grants voting power over gauge emission allocations. Voters select pools, set relative weights, and earn voting rewards: trading fees from pools they vote for plus any external bribes deposited to attract votes. Voting runs weekly from Thursday 00:00 UTC to Wednesday 23:59 UTC.
Points Program — A 6-month incentive program that rewards early liquidity providers and swapper users with Points, which convert to VRT under predefined conversion rules after the program ends. See the Points Program document for full details.
ve(3,3) Model
The ve(3,3) mechanism aligns incentives across all participants:
- Liquidity Providers (unstaked) earn 100% of trading fees from their pool, proportional to their share.
- Liquidity Providers (staked in gauge) forgo trading fees and instead earn VRT emissions directed to that pool's gauge.
- veVRT Voters direct emissions to pools by voting on gauges and earn 100% of trading fees from voted pools plus any external bribes deposited for those gauges.
- veVRT Lockers (non-voters) receive rebases (anti-dilution rewards in VRT) that protect voting power from dilution, but earn no trading fees or bribes.
- Traders access deep liquidity with competitive fees.
The protocol charges no fees and takes no automatic cut from trading — this is by design. To earn as protocol, the team creates veNFTs, votes on gauges, and receives fees and bribes like any other voter. Team funding comes from up to 5% of weekly emissions allocated via the Minter.
Voters who lock longer receive proportionally more voting power (up to 4-year maximum lock). Voting power decreases linearly as the lock period expires.
1.3 Deployed on Base
VIRTUS Protocol is deployed exclusively on Base, an Optimistic Rollup built on the OP Stack that settles to Ethereum Mainnet.
| Property | Detail |
|---|---|
| Network | Base (Chain ID: 8453) |
| Settlement Layer | Ethereum Mainnet (Proof-of-Stake) |
| Rollup Type | Optimistic Rollup (OP Stack) |
| Block Time | ~2 seconds |
| Consensus | Inherits Ethereum PoS security; no independent consensus mechanism |
| Token Standard | ERC-20 (VRT), ERC-721 (veVRT) |
| Smart Contract Language | Solidity |
Base provides low transaction costs, fast confirmation times, and Ethereum-grade security through periodic state commitment and fraud proof mechanisms.
1.4 Contract Addresses
All core contracts are deployed on Base and are publicly verifiable.
| Contract | Address |
|---|---|
| VRT Token (ERC-20) | 0x1CEFF1D2e0F0f0E27417C5600758EEc1606575CA |
| veVRT (VotingEscrow, ERC-721) | 0x6Be687DF2ab94fBD7Eeb4dAc32118110967FF0ef |
| Minter | 0xDc1dE416DdaD4c9e8328F30aE88E2392d5b551f7 |
| Emergency Council | 0xC9C0608F551aDe53f911ceC50F565dB55c5bAFd1 |
Wallet Architecture
| Wallet | Purpose |
|---|---|
| Operational Wallet | Holds genesis VRT allocation; funds operations, grants, liquidity incentives |
| Team Wallet | Holds team VRT for Lock & Vote |
| Deployment Wallet | Executed genesis mint only; no long-term custody or spending role |
2. Dashboard
2.1 Overview
The Dashboard is the central interface for monitoring VIRTUS Protocol activity. It surfaces real-time protocol-wide metrics and individual portfolio data in a single view.
Access the Dashboard at https://virtus-protocol.com/ — no account or login required. Connect a wallet to view personal portfolio data.
2.2 Protocol Metrics
| Metric | Description |
|---|---|
| Total Value Locked (TVL) | Combined USD value of all assets deposited across liquidity pools |
| Trading Volume | Cumulative swap volume across LP Swap and protocol pools |
| Fees Generated | Total trading fees accrued by the protocol's pools |
| Total veVRT | Aggregate veVRT voting power locked across all participants |
| Current Epoch | Active weekly voting epoch (Thursday 00:00 UTC – Wednesday 23:59 UTC) |
All data is sourced directly from on-chain state — no off-chain databases or proprietary APIs.
2.3 User Portfolio
When a wallet is connected, the Dashboard provides a personal summary:
Liquidity Positions — Active deposits across pools, showing current value, pool type (stable / volatile / concentrated), staking status, and accrued fees or emissions.
veVRT Locks — All veNFT positions held by the connected wallet, including remaining lock duration, current voting power, and decay status.
Voting Activity — Gauges voted on during the current epoch, weight allocations, and projected voting rewards (trading fees + bribes).
Claimable Rewards — Pending rewards available for claim: trading fees (for unstaked LP positions or voters), VRT emissions (for staked positions), rebases (for veVRT holders), and external bribes (for voters).
Locked Deposits — Positions with active lock periods, showing expiration dates and available actions. Locked deposits can be staked/unstaked if staking rewards are available, and owners can opt to use accrued fees or rewards as incentives for the pool where they originated.
Points Balance — During the Points Program, accumulated Points from LP activity and Multichain Swapper usage.
2.4 Weekly Epoch Cycle
| Step | Description |
|---|---|
| Start Epoch | New epoch begins, previous votes are finalized |
| Distribute | VRT emissions are distributed to gauges based on vote results |
| Update Claimables | Reward balances are recalculated for voters and stakers |
| Checkpoint | On-chain state is checkpointed for accurate reward accounting |
These functions run automatically via keeper bots. The Dashboard displays the current epoch phase and countdown to the next transition.
3. Swap
VIRTUS Protocol offers two swap engines: LP Swap for on-chain trading through VIRTUS liquidity pools, and Multichain Swap for cross-chain token routing via integrated aggregators.
3.1 LP Swap
LP Swap executes trades directly through VIRTUS Protocol's native liquidity pools on Base. Orders are routed on-chain with no intermediary — the user signs a transaction, and the smart contract settles the swap atomically.
3.1.1 How It Works
- Select the input and output tokens.
- The router identifies the optimal path across available pools (stable, volatile, and concentrated).
- Review the quoted output amount, price impact, and fees.
- Sign and submit the transaction from your connected wallet.
- Tokens are swapped atomically in a single on-chain transaction.
3.1.2 Supported Pairs
LP Swap supports any token pair for which a liquidity pool exists on VIRTUS Protocol. This includes protocol-deployed Blue Fish Pools and any user-created pools. If no direct pair exists, the user may route through Multichain Swapper to make the swap.
3.1.3 Trading Fees
| Pool Type | Description | Default Fee |
|---|---|---|
| Stable | Correlated assets (e.g. USDC/USDT) | Lower default fee |
| Volatile | Uncorrelated assets (e.g. ETH/USDC), standard x·y=k curve | Higher default fee |
| Concentrated (CL) | Slipstream pools with custom price ranges | Varies per pool |
Fee mechanics:
- Default fees apply to all pools of a given type (stable or volatile) unless overridden.
- Custom pool fees completely replace the default fee for that specific pool — they do not add to it.
- Setting a custom fee to 0 removes the override and returns the pool to the default fee.
| LP Status | Trading Fees Go To |
|---|---|
| Not staked | 100% to LP holders, proportional to pool share — claimable anytime |
| Staked in a gauge | 100% to veVRT voters who voted for that pool's gauge — LP stakers receive VRT emissions instead |
3.1.4 Slippage & Price Impact
- Slippage tolerance can be configured before submitting a swap. If the final execution price deviates beyond the tolerance, the transaction reverts.
- Price impact is displayed before confirmation, reflecting how much the swap moves the pool price relative to the quoted rate. Larger trades in lower-liquidity pools produce higher price impact.
3.2 Multichain Swap
The Multichain Swap is a cross-chain token aggregator integrated directly into the VIRTUS interface. It routes swaps across multiple blockchains through external bridge and DEX aggregation providers.
3.2.1 How It Works
- Select the source chain and token.
- Select the destination chain and token.
- The aggregator queries available routes across integrated providers and returns the best quote.
- Review the output amount, route path, estimated time, and fees.
- Sign and submit the transaction from your connected wallet.
- The swap is executed across chains — bridging and swapping are handled automatically by the routing provider.
3.2.2 Supported Chains & Tokens
The Multichain Swap supports tokens and chains available through its integrated routing providers. The set of supported networks and assets expands as providers add coverage. Any token with sufficient liquidity on a supported chain can be routed.
3.2.3 Exchange Fee
The Multichain Swap applies an exchange fee on each executed swap. This fee is collected by the protocol.
3.2.4 Integrated Providers
| Provider | Role |
|---|---|
| Rango Exchange | Cross-chain DEX and bridge aggregator — routes swaps across chains with optimal path selection |
| LiFi | Multi-bridge, multi-DEX aggregation protocol — provides additional routing options and liquidity sources |
Both providers are external services. VIRTUS Protocol does not custody funds during cross-chain swaps — all execution is handled by the respective provider's smart contracts. Users should review provider-specific risks including bridge security, finality times, and potential slippage on destination chains.
3.2.5 Multichain Swap vs LP Swap
| LP Swap | Multichain Swap | |
|---|---|---|
| Scope | Base only | Cross-chain |
| Execution | VIRTUS pool contracts | External aggregators (Rango, LiFi) |
| Fee | Per-pool trading fee (to LPs or voters) | Multichain Swap fee |
| Settlement | Atomic, single transaction | May involve bridging delays |
| Custody | Non-custodial (VIRTUS contracts) | Non-custodial (provider contracts) |
| Points | Yes (during Points Program) | Yes (during Points Program) |
3.3 Wallet Integration
Both swap engines require a connected wallet to sign and submit transactions. Supported wallet connections:
- WalletConnect
- Coinbase Wallet
- Gnosis Safe
VIRTUS Protocol never has access to private keys, seed phrases, or wallet passwords. All transactions are draft messages generated by the interface — the user signs and broadcasts them independently.
4. Pool
The Pool section is where liquidity lives. It covers two functions: Liquidity (browse and manage existing pools) and Deposit (provide liquidity to a pool). Users can also create new pools for any token pair on Base.
4.1 Liquidity
4.1.1 Pool Types
Stable Pools — For correlated assets that maintain similar prices (e.g. USDC/DAI). Use a curve optimized for tight price ranges, enabling low-slippage swaps between pegged or near-pegged assets. Lower default trading fees.
Volatile Pools — For uncorrelated assets with varying prices (e.g. ETH/USDC). Use the standard constant product formula (x·y=k), suitable for general-purpose trading pairs. Higher default trading fees.
Concentrated Liquidity (Slipstream CL) — Allows liquidity providers to concentrate capital within specific price ranges rather than across the full price curve. Improves capital efficiency — LPs earn more fees per dollar deposited when the trading price stays within their selected range. Fees vary per pool.
4.1.2 Blue Fish Pools
Blue Fish Pools are VIRTUS Protocol's flagship liquidity pools, designed around highly liquid asset pairs to attract long-term capital and generate sustainable trading volume.
| Pool | Type | Fee Tiers |
|---|---|---|
| WETH / USDC | Concentrated | 0.01% (TS:1), 0.05% (TS:10), 0.05% (TS:50), 0.3% (TS:100), 1% (TS:200) |
| cbBTC / USDC | Concentrated | Same fee tier structure |
| WETH / cbBTC | Concentrated | Same fee tier structure |
These pools form the foundation for protocol volume, fee generation, and governance activation. They are configured with wide-range concentrated liquidity to balance capital efficiency with broad price coverage.
4.1.3 Fee Tiers
Trading fees are configurable at two levels:
Default fees are applied globally to all pools of a given type (stable or volatile) unless explicitly overridden.
Custom pool fees replace the default fee entirely for a specific pool. They do not stack on top of the default. Setting a custom fee to 0 removes the override and reverts the pool to the default fee.
4.1.4 Fee Routing
| Scenario | Trading Fees | LP Receives |
|---|---|---|
| LP tokens NOT staked | 100% to LP holders, proportional to pool share | Trading fees (claimable anytime) |
| LP tokens staked in gauge | 100% to veVRT voters who voted for that gauge | VRT emissions (instead of fees, claimable anytime) |
This is the core ve(3,3) trade-off: LPs choose between direct fee income (unstaked) or VRT emission rewards (staked), while voters earn the fees from pools they support.
4.1.5 Gauges & Emissions Routing
Each pool can have an associated gauge — a smart contract that distributes weekly VRT emissions to staked LP positions. Emission allocation is determined by veVRT voter weights:
- veVRT holders vote for gauges during each weekly epoch.
- Votes are weighted proportionally based on each voter's allocated weights across selected pools.
- At epoch end, VRT emissions are distributed to gauges in proportion to total votes received.
- Staked LPs in each gauge claim their share of emissions proportional to their liquidity contribution.
Only pools with whitelisted tokens can receive gauge incentives. The Governor address has exclusive permission to manage the token whitelist, preventing spam tokens from entering the voting system.
4.1.6 User-Created Pools
Anyone can deploy a new liquidity pool for any token pair on Base through the Create Pool interface:
- Select two tokens for the pair.
- Choose the pool type: Basic AMM (Stable), Basic AMM (Volatile), or Concentrated Liquidity (Slipstream CL with custom price ranges).
- For volatile pools, enter one token amount — the other is auto-calculated based on the initial price set.
- Deploy the pool contract.
Pool creation is fully permissionless. Once created, a pool is immediately available for trading and liquidity provision. A gauge can be attached through governance to enable emission rewards.
The protocol also locks VRT into user-created pools using maximum voting power as a governance support mechanism, allowing ecosystem expansion without governance risk while maintaining controlled incentives.
4.2 Deposit
4.2.1 How to Provide Liquidity
- Navigate to Pool → Deposit or select a pool from the Liquidity page.
- Select the pool you want to deposit into.
- Enter the amount for one or both tokens (depending on pool type).
- For concentrated liquidity pools, set your desired price range.
- Review the position details and confirm the transaction.
- Sign the transaction from your connected wallet.
Once deposited, your LP position appears on the Dashboard with real-time tracking of value, accrued fees, and staking status.
4.2.2 Position Management
Staking — Stake LP tokens in the pool's gauge (if available) to earn VRT emissions. Staking redirects trading fees to voters — you receive emissions instead.
Unstaking — LP tokens can be unstaked at any time to stop earning emissions and revert to direct fee accrual.
Adding Liquidity — Additional liquidity can be added to an existing position at any time, including locked positions.
Withdrawing — Remove part or all of your liquidity from a pool. Withdrawal returns both tokens proportional to your pool share at current prices. Locked positions can be withdrawn at any time.
Price Range Adjustments — For concentrated liquidity positions, the price range is fixed at deposit time. To change the range, withdraw and re-deposit with a new range. For locked deposits, you must first unlock the deposit, withdraw liquidity, then deposit liquidity into the desired range and re-lock the position to receive VRT token rewards.
4.2.3 Locked Positions (VRT → veVRT)
Locking is the mechanism for earning voting power and governance rights. Users lock VRT tokens to receive veVRT — a vote-escrow NFT that represents locked VRT with governance weight.
Create Lock — Lock VRT → veVRT. Longer lock periods grant more voting power, up to a maximum of 4 years.
Manage Locks:
- Add VRT to an existing locked position to increase voting power.
- Extend lock duration to maintain or increase voting power as time passes.
- Withdrawals are only available after the lock period has ended.
- Voting power decreases linearly as the lock period expires.
Vote on Gauges — Once VRT is locked as veVRT, the holder can vote on pool gauges to direct weekly VRT emissions. To receive trading fees and bribes, veVRT holders must actively vote — non-voters receive only rebases (anti-dilution rewards).
4.2.4 Claiming Rewards
Rewards accrue continuously and can be claimed at any time:
| Reward Type | Who Earns | Condition |
|---|---|---|
| Trading Fees | LP holders (unstaked) | Proportional to pool share |
| VRT Emissions | LP stakers (staked in gauge) | Proportional to staked liquidity |
| Rebases | veVRT holders | Automatic anti-dilution, no action required |
| Bribes | veVRT voters | Proportional to voting weight on the gauge |
If a referral or beneficiary share is set on a position, the respective share of fees or staking rewards is calculated and redirected at claim time automatically.
4.3 Protocol Fee Structure
The protocol charges no automatic fee cut from trading. This is by design under the ve(3,3) model.
| Revenue Source | Destination |
|---|---|
| Trading fees (unstaked pools) | 90% to LP holders – 10% to veVRT voters |
| Trading fees (staked pools) | 100% to veVRT voters for that gauge |
| VRT emissions | To staked LPs via gauges, up to 5% to team via Minter |
| Protocol treasury | No automatic cut — team earns by creating veNFTs, voting on gauges, and receiving fees and bribes like any other participant |
Team emissions are specified in the smart contract, and the Minter can distribute up to 5% of weekly emissions to the team's address via setTeamRate. All funds received are used to support the protocol's development and cover operating costs. The amount stipulated in the contract upon deployment cannot be changed.
5. Governance
VIRTUS Protocol's governance is built on the ve(3,3) model: lock VRT to receive veVRT voting power, vote on pool gauges to direct weekly emissions, and earn rewards for active participation. Governance is accessed through Lock and Vote pages, plus supporting systems including the VRT Exchange, Token Whitelist, and Weekly Tasks.
5.1 Lock
5.1.1 Create Lock
Users lock VRT tokens to receive veVRT — an ERC-721 NFT representing locked VRT with voting power.
- Navigate to Governance → Lock.
- Enter the amount of VRT to lock.
- Select the lock duration.
- Confirm and submit the transaction.
- Receive a veVRT NFT in your wallet.
Lock duration: Minimum 1 week (1 epoch). During the Points Program, the minimum lock period is 3 months. Maximum lock is 4 years. Longer lock = more voting power.
5.1.2 Manage Your Locks
Add VRT — Increase the VRT amount in an existing lock to boost voting power. Available at any time during the lock period.
Extend Duration — Extend the lock period to maintain or increase voting power. Can be extended up to the 4-year maximum.
Withdraw — Available only after the lock period has ended. Partial or full withdrawal of VRT is possible once the lock expires.
Transfer — veVRT NFTs can be transferred to other wallets as standard ERC-721 tokens.
5.1.3 Voting Power Decay
Voting power decays linearly from the moment of locking:
- A 4-year lock starts at maximum voting power and declines to zero over 4 years.
- A 1-year lock starts at 25% of maximum voting power and declines to zero over 1 year.
- To maintain voting power, users can extend their lock duration at any time.
This design rewards long-term commitment and ensures governance influence reflects ongoing alignment with the protocol.
5.2 Vote
5.2.1 How Voting Works
Once VRT is locked as veVRT, holders vote on pool gauges to determine how weekly VRT emissions are distributed. Voters earn rewards in return — trading fees from voted pools plus any external bribes.
- Navigate to Governance → Vote.
- Select one or more pools from the available gauge list.
- Set relative weights for each selected pool.
- Confirm and submit your vote.
Votes are active for the current weekly epoch (Thursday 00:00 UTC – Wednesday 23:59 UTC). At epoch end, emissions are allocated to gauges in proportion to total votes received.
5.2.2 Voting Rewards
Trading Fees — When LP tokens are staked in a gauge, 100% of that pool's trading fees are redirected to the veVRT voters who voted for that gauge. Fees are distributed weekly, proportional to each voter's share of total votes on that gauge.
External Bribes — Anyone can deposit tokens into a gauge to attract votes. Bribe rewards are distributed proportionally to voters on that gauge.
5.2.3 What If You Don't Vote?
veVRT holders who do not vote receive rebases only — anti-dilution rewards in VRT that protect voting power from being diluted by new emissions. Rebases are automatic and require no action, but carry no trading fees or bribe income.
5.2.4 Voting Pools
The Voting Pools view shows all pools where your votes are currently allocated, including weight distribution, projected rewards, and epoch status.
5.3 VRT Exchange
The VRT Exchange allows users to acquire veVRT directly by exchanging tokens — offering better rates for longer commitment periods.
5.3.1 How It Works
- Enter the amount to exchange.
- Select a commitment period — longer periods unlock better rates.
- VRT is converted to veVRT with corresponding voting power.
- Participate in governance: vote for gauges and earn rewards.
5.3.2 Pricing by Lock Duration
| Commitment Period | Price per VRT |
|---|---|
| 4 years (maximum) | $0.01 |
| 1 year | $0.04 |
| 3 months (minimum) | $0.07 |
Pricing scales linearly between reference points. Longer commitment = lower price per VRT.
5.3.3 Key Details
- Accepted assets: all token types, converted to stablecoins via LP Swap or Multichain Swap.
- veVRT received represents locked veVRT NFTs that can be transferred to other wallets as standard ERC-721 tokens.
- Voting power decreases linearly as time passes.
5.4 Bribes & External Incentives
Bribes are a core mechanism for aligning external protocols with VIRTUS governance. Any participant — projects, DAOs, or individual users — can deposit tokens as incentives to attract veVRT votes toward specific pool gauges.
5.4.1 How Bribes Work
- A project deposits tokens (any whitelisted asset) into a gauge as a bribe.
- veVRT voters see available bribes when selecting gauges to vote on.
- Voters who allocate weight to that gauge earn a proportional share of the deposited bribe.
- Bribes are distributed weekly alongside trading fees at epoch end.
Bribes create a competitive market for emissions: pools that generate more value attract more bribe capital, which attracts more votes, which directs more emissions — reinforcing a flywheel of liquidity and activity.
5.5 Emission Schedule
Upon completion of the Points Program, the Smart Contract automatically initiates VRT token weekly emission. Emissions follow a predefined schedule with variable weekly minting governed by fixed coefficients — not subject to any adjustment.
5.5.1 Phases
| Phase | Period | Weekly Emission | Coefficient |
|---|---|---|---|
| Points Program | Weeks 1–24 | 0 VRT | — |
| Initiation | Weeks 25–40 | Starting at 10,000,000 VRT, increasing weekly | 1.03 per week |
| Elevation | Weeks 41–50 | Stabilized | 1.0 per week |
| Perfection | Weeks 51–∞ | Gradually decreasing | 0.99 per week |
The emission pool is not limited to a fixed period and continues throughout the full lifecycle of the protocol.
5.5.2 Emission Distribution
| Recipient | Share |
|---|---|
| Liquidity Providers (staked in gauges) | ~100% of weekly emissions |
| Team (via Minter setTeamRate) | Up to 5% of weekly emissions |
5.5.3 Design Principles
- Early-stage emissions are intentionally conservative to limit sell pressure during low-liquidity phases.
- Emissions increase as protocol usage, liquidity, and fee revenue expand.
- Emissions peak in the mid-cycle and then progressively decline, reinforcing scarcity and long-term alignment.
- VRT emission is unlimited in duration and follows predefined emission coefficients rather than a fixed supply cap.
5.6 Token Whitelist
- Only whitelisted tokens can be used in pools that receive voting incentives and VRT emissions.
- This prevents spam tokens from entering the voting system and diluting governance quality.
- The Governor address has exclusive permission to add or remove tokens from the whitelist.
Non-whitelisted tokens can still be used in pools, but those pools cannot receive gauge emissions or be voted on.
5.7 Weekly Tasks
Protocol maintenance runs on a weekly cycle, aligned with the voting epoch. These functions execute automatically via keeper bots.
| Step | Order | Description |
|---|---|---|
| Start Epoch | 1 | Begins a new epoch; finalizes previous votes |
| Distribute | 2 | Distributes VRT emissions to gauges based on vote results |
| Update Claimables | 3 | Recalculates reward balances for voters and stakers |
| Checkpoint | 4 | Checkpoints on-chain state for accurate reward accounting |
The sequence must execute in order: Start Epoch → Distribute → Update Claimables → Checkpoint.
5.8 Emergency Council
| Property | Detail |
|---|---|
| Contract | 0xC9C0608F551aDe53f911ceC50F565dB55c5bAFd1 |
| Type | Multisig |
| Scope | Emergency actions only — cannot modify core protocol parameters, emission schedules, or user funds |
The Emergency Council exists as a safety mechanism during the protocol's early growth phase. Its powers are intentionally constrained and subject to progressive decentralization as governance matures.
5.9 Anti-Capture Mechanisms
Protocol-Owned Voting Power — The protocol locks VRT with maximum voting power across all pools, ensuring that reward allocation remains filtered and conservative during early stages. This dilutes the influence of any single large participant.
Progressive Governance Introduction — Governance power is introduced gradually and defensively, remaining capital-backed and protocol-stabilized. Users who seek greater influence must exchange their tokens to VRT and lock VRT themselves, creating organic demand.
Predefined Emission Coefficients — Emission rates follow hardcoded coefficients (1.03 → 1.0 → 0.99) that cannot be altered after deployment. This removes discretionary control over supply growth and ensures emissions remain predictable and transparent.
6. Tokenomics
6.1 Token Overview
VRT (ERC-20)
| Property | Detail |
|---|---|
| Token Name | VIRTUS |
| Ticker | VRT |
| Standard | ERC-20 (with multichain support via bridges) |
| Chain | Base (Chain ID: 8453) |
| Contract | 0x1CEFF1D2e0F0f0E27417C5600758EEc1606575CA |
| Maximum Supply | Unlimited |
| Supply Model | Two-phase minting |
veVRT (ERC-721)
| Property | Detail |
|---|---|
| Token Name | Vote-Escrowed VRT |
| Ticker | veVRT |
| Standard | ERC-721 (NFT) |
| Chain | Base (Chain ID: 8453) |
| Contract | 0x6Be687DF2ab94fBD7Eeb4dAc32118110967FF0ef |
| Purpose | Governance voting power, emission direction, fee/bribe rewards |
| Created By | Locking VRT for a chosen duration (1 week – 4 years) |
veVRT is non-fungible — each lock position is represented as a unique NFT with its own lock amount, duration, and decaying voting power.
6.2 Supply Model
VRT uses a two-phase minting model. There are no private rounds, no public sales, and no fundraising allocations.
Phase 1: Genesis Mint — 200,000,000 VRT minted at protocol deployment. Executed by the Deployment Wallet. The Deployment Wallet has no long-term custody or spending role.
Phase 2: Weekly Emission — Unlimited VRT supply minted gradually in accordance with the Emission Schedule. Minting is activity-based, tied to real protocol usage. Parameters are governed by predefined coefficients. Weekly emission is started automatically by the Smart Contract upon completion of the Points Program.
6.3 Initial Distribution (200M VRT)
| Allocation | Amount | Action |
|---|---|---|
| Points Program | 30,000,000 VRT | Distributed to early participants based on LP and Swap activity |
| Initial Liquidity | 50,000,000 VRT | Supplied to Liquidity Pools |
| Grants | 20,000,000 VRT | External/internal contributors expanding protocol functionality |
| Lock & Vote (Team) | 100,000,000 VRT | Locked for maximum duration |
6.4 Emission Schedule
| Phase | Period | Weekly Emission | Coefficient |
|---|---|---|---|
| Points Program | Weeks 1–24 | 0 VRT | — |
| Initiation | Weeks 25–40 | Starting at 10,000,000 VRT, increasing weekly | 1.03 per week |
| Elevation | Weeks 41–50 | Stabilized | 1.0 per week |
| Perfection | Weeks 51–∞ | Gradually decreasing | 0.99 per week |
Emissions follow hardcoded coefficients that cannot be altered once initiated. The emission pool is not limited to a fixed period and continues throughout the full lifecycle of the protocol. VRT emission is unlimited in duration and follows predefined coefficients rather than a fixed supply cap.
6.5 VRT Fed (Democratic Monetary Policy)
The VRT Fed is a future governance mechanism that introduces democratic control over emission parameters. It activates approximately at epoch 100–110, when weekly emission reaches ~9,000,000 VRT per week.
Once active, veVRT holders vote on whether to increase, decrease, or maintain the weekly emission rate. This transitions monetary policy from a fixed coefficient model to a community-governed model, where supply growth is determined by the collective decision of locked token holders.
6.6 Revenue
Protocol revenue is used exclusively to maintain protocol operability, fund ongoing development and improvements, and support advertising and strategic collaborations.
Protocol revenue may also be used for VRT buyback operations, subject to internal controls and performance considerations.
7. Roadmap
VIRTUS Protocol follows a phased deployment strategy designed to build liquidity depth, establish price stability, and activate governance progressively — each phase unlocking the next only when on-chain conditions support it.
7.1 Phase 1: Liquidity Pool Launch & Soft TGE
The protocol launches its core liquidity infrastructure together with a Soft Token Generation Event. The Soft TGE establishes operational stability and incentive alignment without introducing public market pressure or speculative distribution.
No public VRT sale, airdrop, or unrestricted distribution occurs at this stage. All remaining unlimited VRT supply is reserved for controlled, long-term emission governed by the emission schedule.
7.2 Phase 2: Points Program
The Points Program starts upon protocol deployment and runs for 6 months. During this period, users earn Points for activity on the Multichain Swapper, LP Swap, and Liquidity Pools.
7.3 Phase 3: Emission Start
Upon completion of the Points Program, the Smart Contract automatically initiates weekly VRT emission. The protocol transitions to the Initiation emission phase.
7.4 Phase 4: Vote & Lock Activation
Governance becomes fully operational. Vote and Lock pages transition to fully operational.
7.5 Phase 5: DEX Listing
The listing of VRT on decentralized exchanges is executed as a strategic expansion step, not as an initial launch mechanism. The objective is to provide organic market access only after liquidity depth, pricing stability, and governance foundations are in place.
7.6 Future: VRT Fed Activation
Approximately at epoch 100–110, when weekly emission reaches ~9,000,000 VRT/week, the VRT Fed activates. This transitions emission control from predefined coefficients to democratic governance — veVRT holders vote on whether to increase, decrease, or maintain the weekly emission rate.
This milestone marks the protocol's shift to fully community-governed monetary policy.
8. Security
VIRTUS Protocol inherits its smart contract architecture from Velodrome V2, one of the most battle-tested ve(3,3) DEX implementations in production. Security is enforced through professional auditing, immutable contracts, multisignature custody, and transparent on-chain operations.
8.1 Smart Contract Audits
The core codebase was audited by Spearbit during February–March 2023. All critical and high severity issues were fully resolved prior to deployment. Acknowledged findings were reviewed and determined to present acceptable risk within the protocol's design parameters.
Additional audits were completed for the Aerodrome codebase, from which VIRTUS Protocol also inherits components.
The Pool Launcher module was audited by MixBytes (September–October 2025):
8.2 Smart Contract Immutability
Core protocol smart contracts are deployed as immutable — once on-chain, the contract logic cannot be modified, upgraded, or replaced by any party, including the protocol team.
- No backdoors or upgrade proxies in core contracts.
- Emission coefficients (1.03 → 1.0 → 0.99) are hardcoded and cannot be altered after deployment.
- Pool logic, voting mechanics, and fee distribution operate autonomously without any intervention.
- Users interact directly with verified, immutable code — not with changeable proxy contracts.
The protocol is fully permissionless. Anyone can interact with the deployed smart contracts directly, without relying on the VIRTUS interface.
8.3 Multisig Controls
All protocol wallets holding VRT or revenue use multisignature security to prevent single points of failure.
The Deployment Wallet executed the genesis mint only and retains no long-term custody or spending role.
Multisig wallets are operated via Gnosis Safe, requiring multiple independent signers to approve any transaction before execution. This protects against unauthorized access, compromised keys, and unilateral fund movements.
8.4 Emergency Council
| Property | Detail |
|---|---|
| Contract | 0xC9C0608F551aDe53f911ceC50F565dB55c5bAFd1 |
| Type | Multisig |
| Scope | Emergency actions only |
The Emergency Council cannot modify core protocol parameters, emission schedules, or user funds. Its powers are intentionally constrained and subject to progressive decentralization as governance matures.
8.5 Non-Custodial Architecture
VIRTUS Protocol is entirely non-custodial. At no point does the protocol, the interface, or any team member have access to user funds.
- The interface generates draft transaction messages — users sign and broadcast them from their own wallets.
- Private keys, seed phrases, and wallet passwords are never collected, stored, or transmitted.
- All swaps, deposits, locks, and votes are executed by the user directly against on-chain smart contracts.
- Cross-chain swaps via the Multichain Swapper are handled by external provider contracts (Rango, LiFi) — VIRTUS does not custody funds during cross-chain execution.
8.6 On-Chain Transparency
All protocol operations are fully verifiable on-chain:
- Token minting, emission distribution, and fee collection are recorded on the Base blockchain.
- Wallet balances, lock positions, voting weights, and reward claims are publicly visible.
- Smart contract source code is verified and readable on block explorers.
- No off-chain databases or proprietary APIs are involved in core protocol logic.
© 2026 VIRTUS Protocol. All rights reserved.